Skip Headers

Oracle® Database Reference 10g Release 2 (10.2) Part Number B14237-02 |
Home | Book List | Contents | Index | Master Index | Feedback

Previous | Next
| View PDF

# DBA_LOGSTDBY_NOT_UNIQUE

`DBA_LOGSTDBY_NOT_UNIQUE` displays all tables that have no primary and no non-null unique indexes. Most of the tables displayed by this view are supported because their columns contain enough information to be maintained in a logical standby database. Some tables, however, cannot be supported because their columns do not contain the necessary information. Unsupported tables usually contain a column defined using an unsupported datatype.

Column | Datatype | NULL | Description
--- | --- | --- | ---
`OWNER` | `VARCHAR2(30)` |  | Schema name of the non-unique table
`TABLE_NAME` | `VARCHAR2(30)` |  | Table name of the non-unique table
`BAD_COLUMN` | `VARCHAR2(1)` |  | `Y` - Table column is defined using an unbounded data type, such as `LONG` or `BLOB`. If two rows in the table match except in their LOB columns, then the table cannot be maintained properly. Log apply services will attempt to maintain these tables, but you must ensure the application does not allow uniqueness only in the unbounded columns. `N` - Enough column information is present to maintain the table in the logical standby database but the log transport services and log apply services would run more efficiently if you added a primary key. You should consider adding a disabled `RELY` constraint to these tables.